Layer 04 · Memory · Inside WordPress
Your site remembers
what every AI
ever learned here.
The Knowledge Layer is not a feature. It is memory infrastructure — kl_* database tables inside your own WordPress, growing richer with every session. Agents, skills, protocols, session logs, observations. The site itself becomes the shared state between every AI that ever connects.
Knowledge Layer / 01 — In one breath
What it is. Why it exists. How it works. What it brings you.
A reading of the Knowledge Layer before any spec. The shape of it in operator language — what changes the day it's there, why every AI you ever connect benefits from it.
What
A small set of tables inside your WordPress that store what AIs learn here.
Not a content type. Not a custom post. A purpose-built schema — observations, sessions, agents, skills, protocols — designed to be read fast, written safely, and queried by the next AI that connects.
Why
So the next session doesn't start from zero.
Without it, every AI conversation is a goldfish — bright, capable, forgetful. With it, the site itself remembers. The next AI reads what was learned before, then speaks.
How
Bootstrap on connect. Write at session end. Read on next connect.
When an AI connects, it bootstraps from these tables. While the session runs, it writes findings back. The next session — same provider or different — starts already knowing.
What it brings
Compounding intelligence on your server, owned by you.
Memory doesn't live in any provider's context. It lives in your WordPress. Switch from Claude to GPT to Gemini — the site keeps remembering. Sovereign by construction.
Knowledge Layer / 02 — Bootstrap
What the AI reads before it speaks.
Every connected session begins with a read of the Knowledge Layer. Four reads, in order — under a second, finished before the AI types its first word. The AI is now operating from your site's memory, not a blank slate.
Read 01
Agents
The roles your site recognises — editor, support, analyst, ops. The AI picks one based on what you're asking. The role shapes which abilities it considers safe.
Read 02
Skills
Named procedures that have been authored on this site — "do a campaign retro," "audit the taxonomy." The AI can recognise the request and reach for the right one.
Read 03
Protocols
The conventions of this site — how releases are tagged, how customers are addressed, how confidential data is handled. The AI inherits your house style.
Read 04
Observations
What previous sessions learned and saved — quirks, preferences, patterns, decisions, warnings. Compounding context. The reason the AI is faster on visit two than visit one.
Knowledge Layer / 03 — Agents
The AI chooses a role. The role shapes everything.
An agent is not a separate AI. It's a posture the AI adopts — a frame that decides which abilities are reasonable to consider, which skills to reach for, what tone to write in. Three example roles below; you author your own.
Role example
Editor
Concerned with content, voice, structure, scheduling. Reaches for the editorial-intelligence abilities. Won't touch users, plugins, filesystem.
scopes: content · taxonomies · revisions
Role example
Operator
Concerned with state, configuration, performance. Reaches for diagnostics, cron, options, themes, plugins. Confirms before destructive moves.
scopes: site state · operations · diagnostics
Role example
Support
Concerned with people. Reaches into FluentSupport, FluentCRM, FluentCart in that order. Drafts replies, never sends without you.
scopes: tickets · contacts · orders
Knowledge Layer / 04 — Memory vs log
Not logging. Operational memory.
A log records what happened. Operational memory records what was learned — and the next session reads it before speaking. The distinction is the whole point.
What others build
A log.
Records what was done. Filed away. Read by humans during incidents.
A log accumulates. It does not change behaviour. The next session is identical to the first one — same questions, same answers, same blind spots. Useful for audit. Useless for compounding.
What KL is
Operational memory.
Records what was learned. Read by the next AI before it speaks.
Findings, decisions, quirks, preferences. The next session begins by reading them — and so it skips the rediscovery, asks better questions, lands closer on the first try. The site itself gets sharper across visits.
Knowledge Layer / 05 — Handoff
AI-to-AI handoff. Provider-agnostic. Sovereign.
The Knowledge Layer is the handoff. Whatever any AI learned here is readable by whatever AI connects next — same provider or different, same product or different. The site is the shared state. The provider is interchangeable.
Monday session
Claude
writes observations on close
Wednesday session
GPT
writes observations on close
Friday session
Gemini
writes observations on close
Inside WordPress
Knowledge Layer
kl_observations
kl_sessions
kl_agents · kl_skills · kl_protocols
Next session
Whoever connects.
reads the layer, then speaks
Owned by
You.
in your database, on your server
Locked into
No one.
no provider holds the memory
Knowledge Layer / 06 — The schema
Five tables. Inside your own WordPress.
The whole layer is five purpose-built tables on the WordPress database your site already has. No external store. No vector cloud. No SaaS. Migrate the site, the memory comes with it.
kl_agents
The roles.
Named postures the AI can adopt — and the scope shape each one carries.
kl_skills
The procedures.
Named multi-step jobs that have been authored on this site for an AI to execute.
kl_protocols
The conventions.
House style — release tags, voice rules, redaction policies, data-handling boundaries.
kl_sessions
The visits.
Who connected, when, with what scope, with which agent — the audit anchor for everything else.
kl_observations
The findings.
What was learned in a session and saved for the next one. The compounding part. The reason it works.
Knowledge Layer / 07 — How it relates
A consequence — not a fourth Trinity piece. What becomes possible the moment the Trinity is in place.
The Trinity is three: Abilities MCP, MCP Adapter, Abilities for AI. The Knowledge Layer is what the operating layer makes practical — memory that lives on your site, growing richer with every session, owned by you.
Trinity · Layer 01
The bridge that runs on your machine and routes the call to the right site.
Trinity · Layer 02
The gate on each site that authenticates, validates, redacts, and returns.
Trinity · Layer 03
Every WordPress surface registered as a callable named operation behind the gate.
